style(ios): adjust to changes after clang-format update #14050
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
clang-formatwas updated as part of #13886, this would have bought along some changes with the expected formatting.I ran
npm cito install the fresh dependencies, thennpm run format:iosto format the iOS codebase to make it pass the updated formatting rules.I've also removed the pnpm lockfile, I'm not sure when it was committed but it hasn't been touched in a year and this project should not just switch to pnpm. It would impact the entire build process for the SDK if we did that and is probably a larger undertaking